Please address the comments from this code review:

## Overall Comments
- In `binding_test.py`'s `__main__` block you've commented out all existing test calls and only run `test_kwin_controller_create`; this effectively disables the rest of the binding tests when the file is run directly, so either restore those calls or move the KWin-specific test into the existing sequence.
- In `KWinController.__init__`, calling `Library.framework().MaaKWinControllerCreate` without checking for its presence will raise an `AttributeError` at import time in environments where the symbol is missing; consider guarding this with `hasattr` or a try/except and raising a clearer, controlled `RuntimeError` instead of relying on tests to handle the `AttributeError`.

## Individual Comments

### Comment 1
<location path="source/binding/Python/maa/controller.py" line_range="1095" />
<code_context>
+        self._set_kwin_api_properties()
+
+        self._handle = Library.framework().MaaKWinControllerCreate(
+            device_node.encode(),
+            screen_width,
+            screen_height,
</code_context>
<issue_to_address>
**suggestion (bug_risk):** Consider normalizing `device_node` more defensively before encoding.

This assumes `device_node` is a `str` and uses the default encoding. If a `pathlib.Path` or `bytes` is passed, this can fail or double-encode. Using `os.fspath(device_node)` with `os.fsencode(...)`, or at least validating the type, would make this safer for typical path-like inputs and non-ASCII paths.

Suggested implementation:

```python
        super().__init__()
        self._set_kwin_api_properties()

        normalized_device_node = os.fsencode(os.fspath(device_node))

        self._handle = Library.framework().MaaKWinControllerCreate(
            normalized_device_node,
            screen_width,
            screen_height,
            MaaBool(use_win32_vk_code),
        )

```

1. Ensure `os` is imported at the top of `source/binding/Python/maa/controller.py`, e.g. `import os`.
2. If this module already defines a helper for path normalization/encoding, prefer using that helper instead of introducing the `normalized_device_node` variable directly, to stay consistent with the rest of the codebase.
</issue_to_address>